Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1476

reference: 521-tree-1
name: 1476
tree-preservation-order: undefined
521-tpo-1
uprn
address-text
point: POINT (-1.022737 50.899080)
geometry: MULTIPOLYGON (((-1.022708 50.899077,-1.022713 50.899088,-1.022720 50.899092,-1.022736 50.899095,-1.022753 50.899092,-1.022764 50.899083,-1.022765 50.899077,-1.022764 50.899072,-1.022760 50.899067,-1.022754 50.899063,-1.022746 50.899060,-1.022737 50.899059,-1.022720 50.899062,-1.022714 50.899066,-1.022710 50.899071,-1.022708 50.899077)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL